feat(quota): ✨ implement authoritative local counting and retry tracking #82
Conversation
Updates the usage tracking logic to handle providers where local counting is more accurate than API returns (specifically Antigravity). - Implement `sync_mode` in `UsageManager` (`force`, `if_exhausted`, `none`) to control how API baselines affect local counters. - Configure Antigravity credential manager to treat local counting as authoritative, skipping background refreshes to prevent valid usage data from being overwritten by stale API data. - Add `on_retry_attempt` callback in `RotatingClient` and `AntigravityProvider` to track internal retries (bare 429s, empty responses) that consume quota. - Introduce `measured_max_requests` tracking to dynamically learn the actual request limit of credentials.
|
@b3nw This is my take. Though, this feels way too bloated to commit without a major rethink. What do you think? Difference here is that antigravity now only counts locally, except for first fetch and force fetch from the API. But, the retries in the provider make incrementing counts.. difficult. |
Oh i know it is the case. No need to confirm for me - this is because of reporting in 20% increments. So api fetches are essentially useless for measuring quota accurately. It is also rounded a bit, as you can get quota exhausted before you get the error. Suggesting the api refresh happened and you got hit with 0 remaining. |
Updates the usage tracking logic to handle providers where local counting is more accurate than API returns (specifically Antigravity).
sync_modeinUsageManager(force,if_exhausted,none) to control how API baselines affect local counters.on_retry_attemptcallback inRotatingClientandAntigravityProviderto track internal retries (bare 429s, empty responses) that consume quota.measured_max_requeststracking to dynamically learn the actual request limit of credentials.Linked to Bug: Quota count resets unexpectedly when background refresh syncs with API #75 and fix(usage_manager): 🐛 prevent stale API responses from resetting quota count (#75) #81
Important
Enhance quota tracking and retry handling for Antigravity by implementing local counting, retry tracking, and dynamic request limit learning.
sync_modeinUsageManagerto control API baseline effects on local counters (force,if_exhausted,none).on_retry_attemptcallback inRotatingClientandAntigravityProviderto track retries (bare 429s, empty responses).measured_max_requeststracking to learn actual request limits.increment_request_count()inUsageManagerto track retries not covered byrecord_success/record_failure.update_quota_baseline()inUsageManagerupdated to handlesync_modeand trackmeasured_max_requests.run_background_job()ingemini_credential_manager.pyto disable Antigravity refreshes.This description was created by
for 3137f3b. You can customize this summary. It will automatically update as commits are pushed.